Bolero is the premier Web logging analysis and reporting system for the Macintosh. With Bolero youπll unearth the activity and user demographics that can justify a Web siteπs investment. Bolero shows not only how many visitors are using a site, but where they are coming from, what attracted them, and what they are doing once they arrive.
Bolero's list of features include:
Ä Real-time logging
Ä Logging of single or multiple Web servers simultaneously
Ä Post processing of historical data (WebSTAR *.log files)
Ä Open Database Connectivity (ODBC) support
Ä User-customizable filtering of incoming data
Ä Data is stored in an industry-standard SQL database, giving you unsurpassed
flexibility in reporting
Installing Bolero
Double clicking on the Bolero installer will install the following:
ÄBolero 1.0 for logging your web server activity
ÄButler SQL 2.1 for storing your log information
After you install Bolero, there will be a folder on your hard drive called "Bolero". Within the Bolero folder, there contains a Bulter SQL folder which contains a Butler Preference folder.
Ä Drag the Butler Preference folder into your System folder
Warning: Please note, if you have any previous version or any test drive version of Butler installed on your system, the Butler Preference folder will be written over. Please make a back up of your old Butler Preference folder if required. Any time you re-install Butler it will over write any previous Bulter Preferences.
The Butler SQL server in this package is a fat application, which means that it has been optimized for both 680x0 Macintosh and Power Macintosh computers.
To view Bolero statistics over the Web:
1) Install Tango Enterprise 1.5.3. This will create a Tango folder inside your WebSTAR folder.
2) Located within the Bolero Install Folder is another folder called Bolero. Drag this folder into the Tango folder inside your WebSTAR folder.(Your folders should look like this: WebSTAR/Tango/Bolero).
3) To view your reports, type the following address in your Web browser: <http://your web server/tango/bolero/default.html>
All documentation included with Butler SQL and Bolero is in Adobe Acrobat (.pdf) format. If you do not already have Adobe Acrobat installed on your computer, an Acrobat Reader Installer is included with this package.
What Gets Installed
When installing Bolero, the Easy Install option installs the following components onto your computer:
Ä Bolero, BoleroImporter and supporting files
Ä Apple Shared Library Manager 2.0, if not already present
Ä ODBC 2.1, if not already present
Ä Butler SQL 2.1
_____________________________________________
Thank you for test driving Bolero. If you have any questions or suggestions, please feel free to email our technical support department at <support@everyware.com>
EveryWare Development Corp.
6733 Mississauga Rd., 7th Floor
Mississauga, ON
CANADA
L5N 6J5
toll-free: 1-888-819-2500
tel: (905) 819-1173
fax: (905) 819-1172
www: http://www.everyware.com/
_____________________________________________
Bolero 1.0 Release Notes
There have been some last minute modifications to Bolero that are not reflected in the Administratorπs Guide.
BoleroDatabase: åByteπ data stored as åKilobytesπ
With the exception of the ActivityLog table, all references in the Bolero Administratorπs Guide to the BytesSent, BytesSentToDate, percentBytesSent and averageBytesSent should be referred to as KBytesSent, KBytesSentToDate, percentKBytesSent and averageKBytesSent. Data is stored as kilobytes in these columns, with decimal precision.
Bolero Settings File: [GeneralSettings]
A new user-configurable option has been added to the Bolero Settings file:
[GeneralSettings]
Summaries=On
The ability to disable summary execution completely (Summaries=Off) is very useful, for example, when simultaneously logging a åliveπ web server and also importing several log files from previous weeks or months. Temporarily disabling summary execution will prevent Bolero from unwantingly executing the same summary, or summaries, repeatedly.
Butler SQL: Default Tables
Included with the Bolero package is a file, åDefault Tablesπ which is placed in the root level of the åButler Preferences Folderπ on the Butler SQL server.
Default Tables will improve insert, update and delete times. Following is an excerpt from Butler Tech Note #28:
The ≥Default Tables≤ file is a text file in the åButler Preferences Folderπ with each line representing a different table. The format of every line of the default table file is ≥database!tablename≤ [no quotes] and may have other parameters added after the tablename with comma delimiters. These will include a keyword ≥NOCACHE≤ or ≥CACHE≤. If the keyword doesnπt exist, it defaults to ≥NOCACHE≤ (see the follow section on how caching works). This feature is an APPLICATION level setting and will therefore affect all users.
SYNTAX:
databaseName!tableName ,[cache|noCache]
eg:
dal_demo!customer, cache
dal_demo!orders, noCache
dal_demo!staff
There are two main benefits to be gained by this feature:
A) reduce the number of table open journal entries to reduce journal size;
B) increase OPEN TABLE speeds.
Tables opened in this manner will NOT be defined as OPEN, just prepared for open. That is, while Butler has opened the tables and logged the open into the Butler journal for transaction processing, they are not usable nor displayed by Butler as ≥open≤ until implicitly opened using some DML or explicitly opened with an OPEN TABLE statement. Therefore, DDL statements like ALTER, DROP and CREATE should be unaffected by this feature. BACKUP should also be unaffected by these prepared tables. COMPACT represents a problem because Butler expects all Butler table references to be closed prior to the compact.
Two runtime commands have been implemented to allow manipulation of the DEFAULT TABLES set after server launch. One to unload all default tables, one to reload default tables. There are two times when default tables will be defined, once at boot and whenever the 'load' runtime is submitted by any user. There are two times when default tables will be purged: one at program termination and whenever the unload runtime is submitted by any user.
The runtimes to load or unload the default tables are:
$setruntime(loaddefaulttables, true); /* loads the default tables */
$setruntime(loaddefaulttables, false); /* unloads the default tables */
